Skip to content

release: 0.53.1#104

Open
stainless-app[bot] wants to merge 2 commits into
mainfrom
release-please--branches--main--changes--next
Open

release: 0.53.1#104
stainless-app[bot] wants to merge 2 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app
Copy link
Copy Markdown
Contributor

@stainless-app stainless-app Bot commented May 13, 2026

Automated Release PR

0.53.1 (2026-05-13)

Full Changelog: v0.53.0...v0.53.1


This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions


Note

Low Risk
Low risk release bookkeeping: updates version strings and pins GitHub Actions to specific commit SHAs without changing runtime SDK behavior.

Overview
Prepares the 0.53.1 release by bumping the SDK version references in .release-please-manifest.json, internal/version.go, README.md, and adding a 0.53.1 entry to CHANGELOG.md.

Hardens CI by pinning actions/checkout, actions/setup-go, and actions/github-script to specific commit SHAs in .github/workflows/ci.yml.

Reviewed by Cursor Bugbot for commit 886dbc7. Bugbot is set up for automated code reviews on this repo. Configure here.

stainless-app Bot added 2 commits May 13, 2026 02:40
Pin all GitHub Actions referenced in generated workflows (both
first-party `actions/*` and third-party) to immutable commit SHAs.
Updating pinned actions is now a deliberate codegen-side bump rather
than implicit on every workflow run.
@firetiger-agent
Copy link
Copy Markdown

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

Any PR that changes the kernel API. Monitor changes to API endpoints (packages/api/cmd/api/) and Temporal workflows (packages/api/lib/temporal) in the kernel repo

Reason: This is an automated release PR with no visible changes to API endpoints or Temporal workflows; it appears to be a version bump only.

To monitor this PR anyway, reply with @firetiger monitor this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants